User's Guide

Appendix B. Problem Determination

Check this list of possible error conditions if problems occur.

Make sure that the PC Card is in the socket and that the cable is connected to the PC Card.
You are using EMM386.EXE or another memory manager.
EMM386 is the source of many problems with PC Cards. The problem occurs when EMM386.EXE and the LAN device driver are using the same memory. This is called memory contention. The PC Card will not function correctly if this contention occurs. If you are using Card Services, check to be sure that the memory that Card Services controls is excluded by the memory manager. If you are using a point enabler, be sure that the memory that you use is excluded by the memory manager. As a quick test, you may want to comment out EMM386.EXE in your CONFIG.SYS, reboot, and try the PC Card again.
If the PC Card functions, you will have to edit the EMM386.EXE command to exclude some memory. The PC Card uses 8 KB of memory in two separate areas. These memory areas may be consecutive. See "Using a Memory Manager in DOS Environments" for more information.
You are using Card Services.
During reboot, you hear four alternating tones. This indicates that Card Services was unable to give you one or more resources that your program requested. Resources are I/O ports, interrupt level, and memory locations.
Note: The items in the following paragraph are performed by the installation program.

If you are using the NDIS driver (IBMTOKCS.DOS), edit the PROTOCOL.INI file and see whether you have specified a particular value for the interrupt level or memory locations. This would be indicated by the keywords INTERRUPT=X, MMIO=0xXXXX, or RAM=0xXXXX. If you are using the ODI driver (TOKENCS.COM), edit the NET.CFG file and see whether you have specified a particular value for the interrupt level or memory locations. This would be indicated by the keywords INT X, MEM #1 XXXXX, or MEM #2 XXXXX.
These keywords specify a particular value for these parameters. If you find one or more of these keywords, comment them out by placing a semicolon in front of the keyword. Save the file and reboot your computer. If all three are commented out or are not in PROTOCOL.INI or NET.CFG, the driver is in Autoset mode and lets Card Services determine what values are used by the driver. If you reboot and still receive the alternating beep alarm, there is a problem with Card Services. Check your level of Card Services and ensure that it is the latest available.
You are using a point enabler.
When you use a point enabler, it is essential that the I/O ports, interrupt, memory areas, and slot number that are chosen by the enabler agree with what the LAN device driver is expecting. Problems occur when the enabler has set up certain resources and the LAN device driver is expecting others. Typically, the LAN driver will not initialize. Look at the default values for the interrupt, whether the PC Card is a primary or secondary PC Card (this affects the I/O ports), and where the MMIO memory and the SRAM memory are located. Be sure that the enabler settings and the settings of the LAN driver coincide. By the use of parameters on the command line of the enabler and the parameters for the LAN device driver (in PROTOCOL.INI, NET.CFG, or LSP.INI), you should be able to configure your PC Card to function.
If you believe that you have a hardware problem with the PC Card, run the PC Card diagnostics. See Appendix C. Running the Diagnostics Program.
Check Troubleshooting and Error Codes if your computer displays an error code. If you do not find your error code, use the following information to contact IBM.

Questions, Problems?

World Wide Web

You can download the latest code from the World Wide Web.

On a Web browser:

www.networking.ibm.com/support

IBM Product Support

1-800-772-2227 IBM HelpCenter
1-800-565-3344 HelpPC (Canada)
1-800-237-5511 IBM Support Services

Troubleshooting and Error Codes

Novell NetWare Server Driver Messages

Error Code	Explanation and Action
IBMTOKEN-xx-201	IBM Token-Ring Shared RAM Adapter, Version xxx Explanation: Information only. User Action: None.
IBMTOKEN-xx-202	The IBM Token-Ring Shared RAM Adapter UAA (BIA) is xxx. Explanation: Information only. User Action: None.
IBMTOKEN-xx-203	The IBM Token-Ring Shared RAM Adapter is using an LAA of xxx. Explanation: Information only. User Action: None.
IBMTOKEN-xx-204	Revision level xxx of the IBM Token-Ring Shared RAM Adapter is incompatible with this driver version. Explanation: The Revision ID of the IBM Token-Ring Shared RAM Adapter is not one that is supported by this version of the device driver. This correlation is enforced to ensure an appropriate match between the adapter hardware and the device driver software. User Action: Contact your customer service center for assistance. You might need to upgrade your adapter, use a different version of the device driver, or both.
IBMTOKEN-xx-205	A device driver initialization error occurred (failure code xxx). Explanation: An unexpected error occurred during initialization of the device driver. User Action: Properly shut down the computer and switch off the power to the machine. Restart the computer by switching it on again. If the error persists, contact your customer service center.
IBMTOKEN-xx-206	The configuration parameter xxx was specified improperly. Its default value will be used. Explanation: The value of a configuration parameter was improperly specified. User Action: Edit the configuration file (or rerun the configuration program) to specify a value that is of the correct type and within the allowed range. Check the adapter installation instructions for additional information.
IBMTOKEN-xx-207	The configuration parameter values have forced the internal data blocks to exceed the allowed limit. Explanation: The combination of configuration parameters being used requires more than the 64-KB memory area that is available for this adapter instance to hold its internal control information. User Action: Lower the value of the MaxTransmits or MinRcvBuffs parameters from their current setting to reduce the amount of control block storage required by the device driver. Shut down and restart to activate this configuration change.
IBMTOKEN-xx-208	Unable to register interrupt level xxx for this adapter. Explanation: The hardware interrupt level assigned to this adapter was not able to be registered (or hooked) by the device driver. User Action: Check the configuration of your computer, looking for other devices that are assigned the same interrupt level as this adapter. Try removing the conflicting device from the machine and restart the computer to see if the problem goes away. If so, then determine if he conflicting device can be left out of the machine, or if the machine can be reconfigured to resolve the conflict. Note that in most machines, the BIOS assigns certain system resources to the devices found in the computer, including the interrupt level.
IBMTOKEN-xx-210	A hardware failure occurred while attempting to open the adapter. Explanation: An adapter hardware error was detected when opening the adapter for network operation. User Action: Run the adapter diagnostics program to isolate the problem and contact your customer service center. If no problem was identified by the diagnostics, check that the cable is attached securely to both the adapter and the network interface (wall plate). Turn the computer off and then on again to restart the machine. If the problem persists, contact your customer service center.
IBMTOKEN-xx-211	A possible lobe wire failure was detected while attempting to insert into the network. Explanation: The adapter is not correctly connected to the Token-Ring network. User Action: Check that the cable is securely attached to both the adapter and to the Token-Ring network. You might need to contact your local network administrator to ensure that the cabling in the building is intact and that the network concentrator to which you are attached is operational. If the error persists, try using a different cable.
IBMTOKEN-xx-212	A signal loss condition was detected while attempting to insert into the network. Explanation: The Token-Ring network is not functioning correctly. User Action: Contact your local network administrator to determine the status of your network, or try connecting again at a later time.
IBMTOKEN-xx-213	The lobe wire connected to the adapter is not attached to the network. Explanation: The adapter is not correctly connected to the Token-Ring network. User Action: Check that the cable is securely attached to both the adapter and to the Token-Ring network. You might need to contact your local network administrator to ensure that the cabling in the building is intact and that the network concentrator to which you are attached is operational. If the error persists, try using a different cable.
IBMTOKEN-xx-214	The configured data rate for the adapter does not match that of the network. Explanation: The operational speed of the Token-Ring network does not match the configured speed of the adapter. User Action: Change the setting of the DataRate configuration parameter to match the speed of the network to which the adapter is attached. Your local network administrator should be able to tell you which speed to use. Setting the DataRate parameter value to AUTO will allow the adapter to automatically determine the correct speed setting to use when connecting to the network, provided that this is not the only adapter active on the Token Ring. Consult the adapter installation instructions for additional information on setting the DataRate parameter.
IBMTOKEN-xx-215	An adapter timeout occurred while attempting to insert into the network. Explanation: The Token-Ring network is not functioning correctly. User Action: Contact your local network administrator to determine the status of your network, or try connecting again at a later time.
IBMTOKEN-xx-216	A ring failure condition was detected while attempting to insert into the network. Explanation: The Token-Ring network is not functioning correctly. User Action: Contact your local network administrator to determine the status of your network, or try connecting again at a later time.
IBMTOKEN-xx-217	A ring beaconing condition was detected while attempting to insert into the network. Explanation: The Token-Ring network is not functioning correctly. User Action: Contact your local network administrator to determine the status of your network, or try connecting again at a later time.
IBMTOKEN-xx-218	A duplicate network address was detected while attempting to insert into the network. Explanation: The address specified for the NetAddress configuration parameter is being used by another adapter (or ring station) on the network. User Action: Modify the configuration file to change the NetAddress parameter value being used for this adapter, or remove the NetAddress parameter to allow the adapter's burned-in address (universally administered address) to be used. Contact your local network administrator for assistance with choosing a new NetAddress parameter value, or to possibly have the conflicting adapter removed from the same Token-Ring network as this adapter.
IBMTOKEN-xx-219	A ring parameter failure occurred while attempting to insert into the network. Explanation: The Token-Ring network is not functioning correctly. User Action: Contact your local network administrator to determine the status of your network, or try connecting again at a later time.
IBMTOKEN-xx-220	The adapter was forced to remove itself while attempting to insert into the network. Explanation: The Token-Ring network rejected the attempt by this adapter to connect to it. User Action: Contact your local network administrator to determine the status of your network, or try connecting again at a later time.
IBMTOKEN-xx-221	A hardware failure occurred while attempting to open the adapter. Explanation: An adapter hardware error was detected when opening the adapter for network operation. User Action: Run the adapter diagnostics program to isolate the problem and contact your customer service center. If no problem was identified by the diagnostics, check that the cable is attached securely to both the adapter and the network interface (wall plate). Turn the computer off and then on again to restart the machine. If the problem persists, contact your customer service center.
IBMTOKEN-xx-222	A hardware failure occurred while attempting to open the adapter. Explanation: A hardware error was detected when opening the adapter for network operation. User Action: Run the adapter diagnostics program to isolate the problem and contact your customer service center. If no problem was identified by the diagnostics, check that the cable is attached securely to both the adapter and the network interface (wall plate). Turn the computer off and then on again to restart the machine. If the problem persists, contact your customer service center.
IBMTOKEN-xx-223	The adapter cannot be opened in AutoSense mode if it is the only active station on the network. Explanation: The DataRate configuration parameter is set to AUTO (which is also the default value if the parameter is not specified), but the adapter is the first station to open on the Token-Ring network. User Action: This adapter is designed to not open onto the attached Token-Ring network if it is configured to use AutoSense detection and if it would have been the first active ring station. The possible remedies are to try connecting again at a later time when at least one other ring station is active on the network (such as a network server), or to change the configuration value so that the DataRate parameter is set to a specific ring-speed value of M16 or M4 and restart the computer. Note that setting a specific value of M16 or M4 for the DataRate parameter will cause this adapter to establish the operational speed of the Token-Ring network if it is still the first active ring station, so consult with your local network administrator if necessary. Check the adapter installation instructions for additional information on setting the DataRate parameter.
IBMTOKEN-xx-224	Port xxx: The adapter attempted to perform a Remote Program Load but failed monitor contention. Explanation: The adapter was opened as a Remote Proram Load (RPL) client, but was unable to locate an RPL server on the network. User Action: Make sure that there is an active Remote Program Load server on the network and that it is configured to recognize this adapter's network address.
IBMTOKEN-xx-225	A network protocol error occurred while attempting to operate the adapter in full duplex mode. Explanation: The adapter was unable to successfully communicate with a Token-Ring switch when attempting to open for full-duplex operation. User Action: Check that your full-duplex switch is functioning correctly and that the adapter is correctly connected to it. If this problem persists, contact your customer service center.
IBMTOKEN-xx-226	The adapter failed to open during an enhanced mode open sequence. Explanation: The adapter failed during some phase of an enhanced mode open sequence. User Action: Restart the computer. If the problem still occurs run diagnostics. If the diagnostics indicates that the adapter is not defective then record this message number and contact your customer service center.
IBMTOKEN-xx-227	The IBM Token-Ring Shared RAM Adapter opened at xxx Mbps, half duplex. Explanation: Information only. User Action: None.
IBMTOKEN-xx-228	The IBM Token-Ring Shared RAM Adapter opened at xxx Mbps, full-duplex. Explanation: Information only. User Action: None.
IBMTOKEN-xx-229	The adapter is configured for full duplex, but could only be opened in half duplex mode. Explanation: Information only. User Action: None.
IBMTOKEN-xx-233	Adapter analysis code is xxx. Explanation: Information only. User Action: None.
IBMTOKEN-xx-234	Adapter full-duplex operation has now been activated. Explanation: Information only. User Action: None.
IBMTOKEN-xx-240	IBM Token-Ring Shared RAM Adapter Explanation: Information only. User Action: None.
IBMTOKEN-xx-301	ODI 3.3 and Above HSM Explanation: Information only. User Action: None.
IBMTOKEN-xx-304	Adapter is disconnected from the media. Explanation: The media network is not functioning correctly. User Action: Check that the cable is securely attached to both the adapter and the Token-Ring network. Run adapter diagnostics if problems persist. You might need to contact your local administrator to ensure that the cabling in the building is intact and that the network concentrator to which you are attached is operational. If the error persists, try using a different cable.
IBMTOKEN-xx-305	Condition restored. The adapter is connected to the media. Explanation: Information only. User Action: None.
IBMTOKEN-xx-312	Insufficient memory for minimum number of receive buffers. Explanation: The HSM driver was not able to allocate the minimum number of receive buffers. User Action: Increase the number of buffers that the server's operating system can allocate by editing the STARTUP.NCF file on the server. Increase the Minimum Packet Receive Buffers parameter in this file by the total number of transmit (TxBuffers =) and receive (RxBuffers =) that the HSM driver is using. Down and restart the Novell NetWare server.
IBMTOKEN-xx-401	NetWare xxx xxx Explanation: Information only. User Action: None.
IBMTOKEN-xx-402	Unable to find a supported board in this machine. Explanation: Information only. User Action: None.
IBMTOKEN-xx-403	Unable to acquire the configuration parameters for the PCMCIA adapter. Explanation: Needed parameters have not been correctly configured. User Action: Make sure that your computer is loading Card and Socket Services. You must also be loading the Token-Ring 16/4 PC Card Connectivity Enabler (CS20TOK.EXE) in CONFIG.SYS to configure your adapter.

Windows 95 and Windows 98

Windows 95 sometimes has trouble selecting available resources for the PC Card, causing the PC Card not to function. If you find that your PC Card is not functioning, follow this procedure.

Click Start.
Go to the Settings menu selection and click Control Panel.
Click System.
Click the Device Manager tab.
Go to the icon for Network Adapters. You might see a yellow or red circle with an exclamation point inside beside an entry for the IBM Turbo 16/4 Token-Ring PC Card 2. If you see this, click the entry. This will take you to the properties dialog for the PC Card.
Click the Resources tab of the dialog box. There are three resources that must be correct before the IBM Turbo 16/4 Token-Ring PC Card 2 will function correctly. Acceptable values for the input/output range include any four consecutive values beginning at 0300. The interrupt request value should be a value between 3 and 15 that does not conflict with any other devices. The memory range is often set incorrectly by Windows 95. It is recommended that the memory range be set in the 000D0000 to 000DC000 in a non-conflicting memory region. The memory range 000C0000 to 000CFFFF is often used for video caches and Windows 95 does not always exclude memory regions that are already in use.
If EMM386.EXE is in your CONFIG.SYS, comment it out.

Windows NT 3.51 and 4.0 use a point enabler called PCMCIA.SYS that is supplied with Windows NT. PCMCIA.SYS configures the Intel compatible socket controller with settings gleaned from the registry entry for the PC Card. Windows NT will indicate resource conflicts only after an attempt is made to configure a device. As when using a DOS enabler, you must manually choose your PC Card resources. By looking at the event viewer in the administrative tools, you might find that there is an I/O, IRQ, or memory conflict. A program called WINMSD is included with Windows NT which allows you to see the resources of your machine and determine if there are any conflicts. Make a note of your configured resources and compare them to the settings indicated by WINMSD. Make corrections to your configuration as needed. This is done by the following procedure:

Right-click Network Neighborhood.
Select Properties.
Select the Adapter tab.
Select IBM Turbo 16/4 Token-Ring PC Card 2 and click Properties.

You can now change your configuration as needed.

Windows 2000

Windows 2000 sometimes has trouble selecting available resources for the PC Card, causing the PC Card not to function. If you find that your PC Card is not functioning, follow this procedure:

From the Control Panel, double-click the System icon. Select the Hardware tab, and click the Device Manager button.
From the Device Manager, look for a yellow or red circle with an exclamation point beside an entry for the IBM Turbo 16/4 Token-Ring PC Card 2. If you see this, then double-click the adapter. The properties dialog for the adapter will now be displayed.
The device status window will tell you why the device is not functioning. You might choose to try to resolve the problem yourself based on the problem description, or Windows 2000 will help you solve the problem if you click the Troubleshooter button.

OS/2 NDIS Error Codes

The following sections provide messages that can be received from the NDIS driver function. The messages are logged to a file. The NDIS driver signals the user when a Card Services call fails; the error signal is an alternating beep. If you hear this sound, and you are running OS/2, a problem is occurring during configuration of the PC Card and you must review the LANTRAN.LOG file in your \IBMCOM subdirectory to determine what is wrong. Depending on the error, you may see one or more of the following error codes.

Error Code Explanation and Action
LTG0022E A failure during initialization of te IBMTOKCS device driver has occurred. This is a generic

Explanation:
This is a generic initialization failure message. If the IBMTOKCS device driver encounters any errors during initialization, the specific message related to the error will accompany this generic message.
User Action:
Resolve the specific error that accompanies this message. In addition, ensure that the Protocol Manager device driver, PROTMAN.OS2, is located in the \IBMCOM directory, and that a DEVICE statement for PROTMAN.OS2 exists in the CONFIG.SYS file.

LTG0023I An unrecognized parameter was found in PROTOCOL.INI.

Explanation:
The parameter displayed was found while the installation program wa sprocessing the IBM Token-Ring Network Driver section of PROTOCOL.INI. The parameter is not valid.
User Action:
Correct the parameter or remove it from PROTOCOL.INI.

LTG024I A value specified for a parameter in PROTOCOL.INI is not valid.

Explanation:
The value provided for the parameter is not the correct type or is not a valid value.
User Action:
Change the value for the parameter in PROTOCOL.INI.

LTG0025I A configuration error was found in PROTOCOL.INI.

Explanation:
Conflicting parameter values were found while the installation program was processing the IBM Token-Ring Network Driver section of PROTOCOL.INI.
User Action:
Examine the configuration parameters and correct the conflicting values in PROTOCOL.INI.

LTG0026I The PC Card is not responding or was not found.

Explanation:
One of the following conditions has caused this error:

The logical primary or alternate setting in the PROTOCOL.INI file does not map to the physical primary or alternate setting.
The PC Card is not responding to a request to start.
There is no physical PC Card in your computer.

User Action:
If there is already a PC Card in this system, check the logical primary or alternate setting. Check the cable and ensure that the connection to the token-ring network addressable unit is functioning correctly. Then, run the hardware diagnostics for the token-ring PC Card to ensure that the PC Card and options have been installed correctly.
If there is no PC Card in your computer, install a token-ring PC Card or remove the device driver statement from the CONFIG.SYS file.

LTG0027I The protocol manager could not be opened.

Explanation:
An unexpected error occurred when the program attempted to open the protocol manager.
User Action:
Check the drive and directory to ensure that the protocol manager is located in the specified path.

LTG0029I The PC Card encountered a lobe wire fault.

Explanation:
The PC Card will be closed.
User Action:
Perform the following steps:

Check and secure all cable connections between your PC Card and the Multistation Access Unit (MSAU). Correct any related problems and try the operation again.
If there are no related problems, refer to the documentation that was shipped with your PC Card to run diagnostics; then, try the operation again.
If the problem persists, print or save the LANTRAN.LOG file and contact your LAN administrator.

LTG0030I There are not adequate receive bufers for the PC Card to open.

Explanation:
The requested DIR.OPEN.ADAPTER paramaeter has not allowed enough receive buffer space in the PC Card shared-RAM area.
User Action:
Reduce the RAM requirements by reconfiguring the parameters in PROTOCOL.INI. The parameters that will reduce the space requirements for the receive buffer are the transmit buffers (if more than one is specified).

LTG0032I An invalid node address error occurred when the program attempted to open the PC Card.

Explanation:
The node address defined is not valid.
User Action:
Specify a valid node address. Refer to the IBM Token-Ring Network Architecture Reference (SC30-3374) for node address restrictions.

LTG0033I The receive buffer length defined is not valid.

Explanation:
The PC Card was not opened. The receive buffer length defined in PROTOCOL.INI is not valid. The value specified must be greater than the allowable maximum, less than the allowable minimum, or not a multiple of 8.
User Action:
Specify a valid receive buffer length.

LTG0034E The PC Card transmit buffer length defined is not valid.

Explanation:
The PC Card was not opened. The PC Card transmit buffer length defined in PROTOCOL.INI is not valid. The value specified must be greater than the allowable maximum, less than the allowable minimum, or not a multiple of 8.
User Action:
Specify a valid PC Card transmit buffer length.

LTG0037I An unexpected error caused the Open Adapter Command in the IBMTOKCS.OS2 device driver.

Explanation:
The PC Card was closed because of an unexpected error condition.
User Action:
See the message log, LANTRAN.LOG, for additional information about this error. The error must be corrected before you can use this PC Card.

LTG0038I An auto-removal error has been detected.

Explanation:
The PC Card will be closed. The PC Card has either detected a monitor contention failure or received a beacon frame from the ring. The problem might be that your PC Card speed is different from the speed at which the LAN is running.
User Action:
Perform the following steps:

Check and secure all cable connections between your PC Card and the multistation access unit (MSAU). Correct any related problems and try the operation again.
If there are no related problems, run the diagnostics; then, try the operation again.
If the problem persists, print or save the LANTRAN.LOG file and contact your LAN administrator.

LTG0039I A remove medium access control (MAC) frame has been received.

Explanation:
The PC Card will be closed. A command forcing the PC Card to remove itself from the ring has been received.
User Action:
Contact your LAN administrator to determine why the REMOVE command was issued for your computer.

LTG0041I An open error occurred during the lobe media test phase.

Explanation:
The PC Card has detected a problem on your local lobe between the PC Card and the multistation access unit (MSAU).
User Action:
Perform the following steps:

Check and secure all cable connections between your PC Card and the MSAU. Correct any related problems and try the operation again.
If there are no related problems, run the diagnostics; then, try the operation again.

LTG0042I An open error occurred during the physical insertion phase.

Explanation:
The PC Card has detected one of the following open errors while trying to insert into the LAN:

Ring failure
Ring beaconing
Timeout

User Action:
Perform the following steps:

Check and secure all cable connections between your PC Card and the multistation access unit (MSAU). Correct any related problems and try the operation again.
If there are no related problems, run the diagnostics; then, try the operation again.

LTG0043I An open error occurred during the address verification phase.

Explanation:
The PC Card has detected one of the following open errors during the address verification phase of the PC Card open process:

Signal loss
Timeout
Ring failure
Ring beaconing
Duplicate node
REMOVE command received

User Action:
Perform the following steps:

Check and secure all cable connections between your PC Card and the multistation access unit (MSAU). Correct any related problems and try the operation again.
If there are no related problems, run the diagnostics; then, try the operation again.

LTG0044I An open error occurred during the roll-call poll phase.

Explanation:
The PC Card has detected one of the following open errors during the roll-call poll phase of the PC Card open process:

Signal loss
Timeout
Ring failure
Ring beaconing
REMOVE command received

User Action:
Perform the following steps:

Check and secure all cable connections between your PC Card and the multistation access unit (MSAU). Correct any related problems and try the operation again.
If there are no related problems, run the diagnostics; then, try the operation again.
If the problem persists, print or save the LANTRAN.LOG file and contact your LAN administrator.

LTG0045I An open error occurred during the request parameter phase.

Explanation:
The PC Card has detected one of the following open errors during the request parameter phase of the PC Card open process:

Signal loss
Timeout
Ring failure
Ring beaconing
Parameter request
REMOVE command received

User Action:
Perform the following steps:

Check and secure all cable connections between your PC Card and the multistation access unit (MSAU). Correct any related problems and try the operation again.
If there are no related problems, run the diagnostics; then, try the operation again.
If the problem persists, print or save the LANTRAN.LOG file and contact your LAN administrator.

LTG0051I The open error type is function failure.

Explanation:
The PC Card has detected a lobe media failure while trying to open the PC Card.
User Action:
Perform the following steps:

Check and secure all cable connections between your PC Card and the multistation access unit (MSAU). Correct any related problems and try the operation again.
If there are no related problems, run the diagnostics; then try the operation again.
If the problem persists, print or save the LANTRAN.LOG file and contact your LAN administrator.

LTG0052I The open error type is signal loss.

Explanation:
The PC Card has detected a signal loss failure while trying to open the PC Card.
User Action:
Perform the following steps:

Check and secure all cable connections between your PC Card and the multistation access unit (MSAU). Correct any related problems and try the operation again.
If there are no related problems, run the diagnostics; then, try the operation again.
If the problem persists, print or save the LANTRAN.LOG file and contact your LAN administrator.

LTG0055I The open error type is timeout.

Explanation:
The PC Card has detected an insertion timer expiration while trying to open the PC Card. This condition indicates that the ring might be congested, experiencing a high bit-error rate, or is losing an unusually high number of tokens or frames.
User Action:
Perform the following steps:

Check and secure all cable connections between your PC Card and the multistation access unit (MSAU). Correct any related problems and try the operation again.
If there are no related problems, run the diagnostics; then, try the operation again.
If the problem persists, print or save the LANTRAN.LOG file and contact your LAN administrator.

LTG0056I The open error type is ring failure.

Explanation:
The PC Card has detected a ring failure while trying to open the PC Card.
User Action:
Perform the following steps:

Check and secure all cable connections between your PC Card and the multistation access unit (MSAU). Correct any related problems and try the operation again.
If there are no related problems, run the diagnostics; then, try the operation again.
If the problem persists, print or save the LANTRAN.LOG file and contact your LAN administrator.

LTG0057I The open error type is ring beaconing.

Explanation:
The PC Card has detected a monitor contention failure or has received a beacon frame from the ring while trying to open the PC Card.
User Action:
Perform the following steps:

Check and secure all cable connecetions between your PC Card and the multistation access unit (MSAU). Correct any related problems and try the operation again.
If there are no related problems, run the diagnostics; then, try the operation again.
If the problem persists, print or save the LANTRAN.LOG file and contact your LAN administrator.

LTG0058I The open error type is duplicate node address.

Explanation:
The PC Card has detected that another station on the ring has a PC Card address equal to the address specified for your PC Card.
User Action:
Note the identification number of this message and then contact your LAN administrator.

LTG0059I The open error type is parameter request.

Explanation:
The PC Card has detected a parameter request error while trying to open the PC Card.
User Action:
Perform the following steps:

Check and secure all cable connections between your PC Card and the multistation access unit (MSAU). Correct any related problems and try the operation again.
If there are no related problems, refer to the documentation that was shipped with your PC Card to run the diagnostics; then, try the operation again.
If the problem persists, print or save the LANTRAN.LOG file and contact your LAN administrator.

LTG0060I The open error type is REMOVE received.

Explanation:
While attempting to insert into the ring, your computer received a command forcing this PC Card to remove from the ring.
User Action:
Contact your LAN administrator to determine why the REMOVE command was issued for your computer.

LTG0063I Your computer is the first attempting to insert onto the ring in AUTORINGSPEED mode.

Explanation:

User Action:
Either remove the AUTORINGSPEED keyword from PROTOCOL.INI or make sure that another computer is on the network and has set the ring speed. If the problem persists, print or save the LANTRAN.LOG file and contact your LAN administrator.

LTG0064I Physical insertion of your computer onto the ring failed.

Explanation:

User Action:
Check the PC Card configuration and retry the open request. If the problem persists, refer to the documentation that was shipped with your PC Card to run diagnostics; then, try the operation again.

LTG0070I A problem was detected on microcode level 00 00 00 C2 45 50.

Explanation:

User Action:
Request and install engineering change ECA0066, P/N 92F9122, on your system, or use the configuration feature of the LAN Adapter Protocol Support installation program to change the value for the number of transmit buffers to be greater than 1.

LTG0083E Token-Ring Credit Card Request I/O failed.

Explanation:
Card Services would not give IBMTOKCS access to the I/O ports it requested.
User Action:
Make sure that no other PC Cards are using the range of I/O ports that the adapter needs. For a primary PC Card the range is A20-A23. For a secondary PC Card the range is A24-A27.

LTG0084E Token-Ring Credit Card Request IRQ failed.

Explanation:
Card Services would not give IBMTOKCS access to the interrupt request (IRQ) line it requested.
User Action:
Make sure that no other PC Cards are using the IRQ requested. IBMTOKCS defaults to IRQ 9. To change the IRQ that IBMTOKCS uses, add the line INTERRUPT=X to your PROTOCOL.INI file. X can be any one of the following values: 3, 4, 5, 7, 9, 10, or 11. The IRQ chosen should not be used by any other device.

LTG0085E Token-Ring Credit Card RAM Request Window failed.

Explanation:
Card Services would not give IBMTOKCS access to the memory window that it requested.
User Action:
Make sure that no other PC Cards are using the memory window requested. IBMTOKCS defaults the MMIO memory window to CC00 for the primary PC Card ot DC00 for the alternate PC Card. It also defaults the SRAM memory window to D800 for the primary PC Card or D400 for the alternate PC Card. To change the MMIO memory window, add the line MMIO=XXXX to your PROTOCOL.INI file. XXXX can be any unused 8-KB, 16-KB, 32-KB, or 64-KB region in the range C000-DC00. You might also have to asjust the RAMSIZE keyword accordingly.

LTG0086E Token-Ring Credit Card Request Configuration failed.

Explanation:
Card Services would not give IBMTOKCS the configuration that it requested.
User Action:
Try a different interrupt line by using the INTERRUPT=X statement in your PROTOCOL.INI file. X can be any unused interrupt line in the range 3-15.

LTG0087E Token-Ring Credit Card RAM MapMemPage failed.

Explanation:
Card Services would not map the shared-RAM memory on the PC Card to the required memory window.
User Action:
Try changing the memory window. IBMTOKCS defaults the MMIO memory window to CC00 for the primary PC Card or DC00 for the alternate PC Card. It also defaults the SRAM memory window to D800 for the primary PC Card or D400 for the alternate PC Card. To change the MMIO meory window, add the line MMIO=XXXX to your PROTOCOL.INI file. XXXX can be any unused 8-KB region in the range C000-DE00. To change the SRAM memory window, add the line RAM=XXXX to your PROTOCOL.INI file. XXXX can be any unused 8-KB, 16-KB, 32-KB, or 64-KB region in the range C000-DC00. You might also have to adjust the RAMSIZE keyword accordingly.

LTG0090E Token-Ring Credit Card Register Client failed.

Explanation:
Card Services would not register the PC Card callback handler.
User Action:
Make sure that you have Card Services 2.0 (PCMCIA.SYS) correctly installed.

LTG0091E Card Services could not be found.

Explanation:

User Action:
Add the appropriate statements to your CONFIG.SYS file so that Card Services will be installed.

LTG0093E No sockets were found by Card Services.

Explanation:
The Card Services function GetCardServicesInfo reported that there are no sockets in your computer. This can be for any of the following reasons:

Socket Services is not installed or is installed incorrectly.
There are no physical sockets on your computer.
No PC Card with sockets is installed or is installed incorrectly.

User Action:
Perform the following steps:

Make sure that you have Socket Services installed correctly.
Make sure that your computer has physical sockets.
Make sure that you have installed the PC Card correctly.

LTG0094I A Token-Ring Auto 16/4 Credit Card Adapter was not found in any socket in your computer.

Explanation:

User Action:
Insert the PC Card in a socket.

LTG0095E A NETADDRESS must be specified to boot without the PC Card present in a socket.

Explanation:
You attempted to boot your computer without a Token-Ring Auto 16/4 Credit Card Adapter inserted in a socket and without a NETADDRESS.
User Action:
Either insert the PC Card in a socket and reboot your computer or add the NETADDRESS= parameter to PROTOCOL.INI and reboot your computer. By adding the NETADDRESS parameter you can insert the Token-Ring Auto 16/4 Credit Card Adapter after the reboot. Make sure that the address you use is either a locally administered address or the universally administered address on your PC Card. To find out your universally administered address, run the diagnostics program that is on the diskettes that came with your adapter.

LTG0097E Token-Ring Credit Card MMIO RequestWindow failed.

Explanation:
Card Services would not give IBMTOKCS access to the MMIO memory window it requested.
User Action:
Make sure that no other PC Cards are using the memory window requested. IBMTOKCS defaults the MMIO memory window to CC00 for the primary PC Card or DC00 for the alternate PC Card. To change the MMIO memory window, add the line MMIO=XXXX to your PROTOCOL.INI file. XXXX can be any unused 8-KB region in the range C000-DC00.

LTG0098E Token-Ring Credit Card MMIO MapMemPage failed.

Explanation:
Card Services would not map the MMIO memory on the PC Card to the requested memory window.
User Action:
Try changing the MMIO memory window. IBMTOKCS defaults the MMIO memory window to CC00 for the primary PC Card or DC00 for the alternate PC Card. To change the MMIO memory window, add the line MMIO=XXXX to your PROTOCOL.INI file. XXXX can be any unused 8-KB region in the range C000-DC00.

LTG0099E PROTOCOL.INI did not have a section with a DriverName=IBMTCS$ keyword.

Explanation:
A common cause of this is not using LAPS to install new drivers.
User Action:
Use LAPS to install the new PC Card Token-Ring Driver.

Error Code	Explanation and Action
LTG0022E	A failure during initialization of te IBMTOKCS device driver has occurred. This is a generic Explanation: This is a generic initialization failure message. If the IBMTOKCS device driver encounters any errors during initialization, the specific message related to the error will accompany this generic message. User Action: Resolve the specific error that accompanies this message. In addition, ensure that the Protocol Manager device driver, PROTMAN.OS2, is located in the \IBMCOM directory, and that a DEVICE statement for PROTMAN.OS2 exists in the CONFIG.SYS file.
LTG0023I	An unrecognized parameter was found in PROTOCOL.INI. Explanation: The parameter displayed was found while the installation program wa sprocessing the IBM Token-Ring Network Driver section of PROTOCOL.INI. The parameter is not valid. User Action: Correct the parameter or remove it from PROTOCOL.INI.
LTG024I	A value specified for a parameter in PROTOCOL.INI is not valid. Explanation: The value provided for the parameter is not the correct type or is not a valid value. User Action: Change the value for the parameter in PROTOCOL.INI.
LTG0025I	A configuration error was found in PROTOCOL.INI. Explanation: Conflicting parameter values were found while the installation program was processing the IBM Token-Ring Network Driver section of PROTOCOL.INI. User Action: Examine the configuration parameters and correct the conflicting values in PROTOCOL.INI.
LTG0026I	The PC Card is not responding or was not found. Explanation: One of the following conditions has caused this error: The logical primary or alternate setting in the PROTOCOL.INI file does not map to the physical primary or alternate setting. The PC Card is not responding to a request to start. There is no physical PC Card in your computer. User Action: If there is already a PC Card in this system, check the logical primary or alternate setting. Check the cable and ensure that the connection to the token-ring network addressable unit is functioning correctly. Then, run the hardware diagnostics for the token-ring PC Card to ensure that the PC Card and options have been installed correctly. If there is no PC Card in your computer, install a token-ring PC Card or remove the device driver statement from the CONFIG.SYS file.
LTG0027I	The protocol manager could not be opened. Explanation: An unexpected error occurred when the program attempted to open the protocol manager. User Action: Check the drive and directory to ensure that the protocol manager is located in the specified path.
LTG0029I	The PC Card encountered a lobe wire fault. Explanation: The PC Card will be closed. User Action: Perform the following steps: Check and secure all cable connections between your PC Card and the Multistation Access Unit (MSAU). Correct any related problems and try the operation again. If there are no related problems, refer to the documentation that was shipped with your PC Card to run diagnostics; then, try the operation again. If the problem persists, print or save the LANTRAN.LOG file and contact your LAN administrator.
LTG0030I	There are not adequate receive bufers for the PC Card to open. Explanation: The requested DIR.OPEN.ADAPTER paramaeter has not allowed enough receive buffer space in the PC Card shared-RAM area. User Action: Reduce the RAM requirements by reconfiguring the parameters in PROTOCOL.INI. The parameters that will reduce the space requirements for the receive buffer are the transmit buffers (if more than one is specified).
LTG0032I	An invalid node address error occurred when the program attempted to open the PC Card. Explanation: The node address defined is not valid. User Action: Specify a valid node address. Refer to the IBM Token-Ring Network Architecture Reference (SC30-3374) for node address restrictions.
LTG0033I	The receive buffer length defined is not valid. Explanation: The PC Card was not opened. The receive buffer length defined in PROTOCOL.INI is not valid. The value specified must be greater than the allowable maximum, less than the allowable minimum, or not a multiple of 8. User Action: Specify a valid receive buffer length.
LTG0034E	The PC Card transmit buffer length defined is not valid. Explanation: The PC Card was not opened. The PC Card transmit buffer length defined in PROTOCOL.INI is not valid. The value specified must be greater than the allowable maximum, less than the allowable minimum, or not a multiple of 8. User Action: Specify a valid PC Card transmit buffer length.
LTG0037I	An unexpected error caused the Open Adapter Command in the IBMTOKCS.OS2 device driver. Explanation: The PC Card was closed because of an unexpected error condition. User Action: See the message log, LANTRAN.LOG, for additional information about this error. The error must be corrected before you can use this PC Card.
LTG0038I	An auto-removal error has been detected. Explanation: The PC Card will be closed. The PC Card has either detected a monitor contention failure or received a beacon frame from the ring. The problem might be that your PC Card speed is different from the speed at which the LAN is running. User Action: Perform the following steps: Check and secure all cable connections between your PC Card and the multistation access unit (MSAU). Correct any related problems and try the operation again. If there are no related problems, run the diagnostics; then, try the operation again. If the problem persists, print or save the LANTRAN.LOG file and contact your LAN administrator.
LTG0039I	A remove medium access control (MAC) frame has been received. Explanation: The PC Card will be closed. A command forcing the PC Card to remove itself from the ring has been received. User Action: Contact your LAN administrator to determine why the REMOVE command was issued for your computer.
LTG0041I	An open error occurred during the lobe media test phase. Explanation: The PC Card has detected a problem on your local lobe between the PC Card and the multistation access unit (MSAU). User Action: Perform the following steps: Check and secure all cable connections between your PC Card and the MSAU. Correct any related problems and try the operation again. If there are no related problems, run the diagnostics; then, try the operation again.
LTG0042I	An open error occurred during the physical insertion phase. Explanation: The PC Card has detected one of the following open errors while trying to insert into the LAN: Ring failure Ring beaconing Timeout User Action: Perform the following steps: Check and secure all cable connections between your PC Card and the multistation access unit (MSAU). Correct any related problems and try the operation again. If there are no related problems, run the diagnostics; then, try the operation again.
LTG0043I	An open error occurred during the address verification phase. Explanation: The PC Card has detected one of the following open errors during the address verification phase of the PC Card open process: Signal loss Timeout Ring failure Ring beaconing Duplicate node REMOVE command received User Action: Perform the following steps: Check and secure all cable connections between your PC Card and the multistation access unit (MSAU). Correct any related problems and try the operation again. If there are no related problems, run the diagnostics; then, try the operation again.
LTG0044I	An open error occurred during the roll-call poll phase. Explanation: The PC Card has detected one of the following open errors during the roll-call poll phase of the PC Card open process: Signal loss Timeout Ring failure Ring beaconing REMOVE command received User Action: Perform the following steps: Check and secure all cable connections between your PC Card and the multistation access unit (MSAU). Correct any related problems and try the operation again. If there are no related problems, run the diagnostics; then, try the operation again. If the problem persists, print or save the LANTRAN.LOG file and contact your LAN administrator.
LTG0045I	An open error occurred during the request parameter phase. Explanation: The PC Card has detected one of the following open errors during the request parameter phase of the PC Card open process: Signal loss Timeout Ring failure Ring beaconing Parameter request REMOVE command received User Action: Perform the following steps: Check and secure all cable connections between your PC Card and the multistation access unit (MSAU). Correct any related problems and try the operation again. If there are no related problems, run the diagnostics; then, try the operation again. If the problem persists, print or save the LANTRAN.LOG file and contact your LAN administrator.
LTG0051I	The open error type is function failure. Explanation: The PC Card has detected a lobe media failure while trying to open the PC Card. User Action: Perform the following steps: Check and secure all cable connections between your PC Card and the multistation access unit (MSAU). Correct any related problems and try the operation again. If there are no related problems, run the diagnostics; then try the operation again. If the problem persists, print or save the LANTRAN.LOG file and contact your LAN administrator.
LTG0052I	The open error type is signal loss. Explanation: The PC Card has detected a signal loss failure while trying to open the PC Card. User Action: Perform the following steps: Check and secure all cable connections between your PC Card and the multistation access unit (MSAU). Correct any related problems and try the operation again. If there are no related problems, run the diagnostics; then, try the operation again. If the problem persists, print or save the LANTRAN.LOG file and contact your LAN administrator.
LTG0055I	The open error type is timeout. Explanation: The PC Card has detected an insertion timer expiration while trying to open the PC Card. This condition indicates that the ring might be congested, experiencing a high bit-error rate, or is losing an unusually high number of tokens or frames. User Action: Perform the following steps: Check and secure all cable connections between your PC Card and the multistation access unit (MSAU). Correct any related problems and try the operation again. If there are no related problems, run the diagnostics; then, try the operation again. If the problem persists, print or save the LANTRAN.LOG file and contact your LAN administrator.
LTG0056I	The open error type is ring failure. Explanation: The PC Card has detected a ring failure while trying to open the PC Card. User Action: Perform the following steps: Check and secure all cable connections between your PC Card and the multistation access unit (MSAU). Correct any related problems and try the operation again. If there are no related problems, run the diagnostics; then, try the operation again. If the problem persists, print or save the LANTRAN.LOG file and contact your LAN administrator.
LTG0057I	The open error type is ring beaconing. Explanation: The PC Card has detected a monitor contention failure or has received a beacon frame from the ring while trying to open the PC Card. User Action: Perform the following steps: Check and secure all cable connecetions between your PC Card and the multistation access unit (MSAU). Correct any related problems and try the operation again. If there are no related problems, run the diagnostics; then, try the operation again. If the problem persists, print or save the LANTRAN.LOG file and contact your LAN administrator.
LTG0058I	The open error type is duplicate node address. Explanation: The PC Card has detected that another station on the ring has a PC Card address equal to the address specified for your PC Card. User Action: Note the identification number of this message and then contact your LAN administrator.
LTG0059I	The open error type is parameter request. Explanation: The PC Card has detected a parameter request error while trying to open the PC Card. User Action: Perform the following steps: Check and secure all cable connections between your PC Card and the multistation access unit (MSAU). Correct any related problems and try the operation again. If there are no related problems, refer to the documentation that was shipped with your PC Card to run the diagnostics; then, try the operation again. If the problem persists, print or save the LANTRAN.LOG file and contact your LAN administrator.
LTG0060I	The open error type is REMOVE received. Explanation: While attempting to insert into the ring, your computer received a command forcing this PC Card to remove from the ring. User Action: Contact your LAN administrator to determine why the REMOVE command was issued for your computer.
LTG0063I	Your computer is the first attempting to insert onto the ring in AUTORINGSPEED mode. Explanation: User Action: Either remove the AUTORINGSPEED keyword from PROTOCOL.INI or make sure that another computer is on the network and has set the ring speed. If the problem persists, print or save the LANTRAN.LOG file and contact your LAN administrator.
LTG0064I	Physical insertion of your computer onto the ring failed. Explanation: User Action: Check the PC Card configuration and retry the open request. If the problem persists, refer to the documentation that was shipped with your PC Card to run diagnostics; then, try the operation again.
LTG0070I	A problem was detected on microcode level 00 00 00 C2 45 50. Explanation: User Action: Request and install engineering change ECA0066, P/N 92F9122, on your system, or use the configuration feature of the LAN Adapter Protocol Support installation program to change the value for the number of transmit buffers to be greater than 1.
LTG0083E	Token-Ring Credit Card Request I/O failed. Explanation: Card Services would not give IBMTOKCS access to the I/O ports it requested. User Action: Make sure that no other PC Cards are using the range of I/O ports that the adapter needs. For a primary PC Card the range is A20-A23. For a secondary PC Card the range is A24-A27.
LTG0084E	Token-Ring Credit Card Request IRQ failed. Explanation: Card Services would not give IBMTOKCS access to the interrupt request (IRQ) line it requested. User Action: Make sure that no other PC Cards are using the IRQ requested. IBMTOKCS defaults to IRQ 9. To change the IRQ that IBMTOKCS uses, add the line INTERRUPT=X to your PROTOCOL.INI file. X can be any one of the following values: 3, 4, 5, 7, 9, 10, or 11. The IRQ chosen should not be used by any other device.
LTG0085E	Token-Ring Credit Card RAM Request Window failed. Explanation: Card Services would not give IBMTOKCS access to the memory window that it requested. User Action: Make sure that no other PC Cards are using the memory window requested. IBMTOKCS defaults the MMIO memory window to CC00 for the primary PC Card ot DC00 for the alternate PC Card. It also defaults the SRAM memory window to D800 for the primary PC Card or D400 for the alternate PC Card. To change the MMIO memory window, add the line MMIO=XXXX to your PROTOCOL.INI file. XXXX can be any unused 8-KB, 16-KB, 32-KB, or 64-KB region in the range C000-DC00. You might also have to asjust the RAMSIZE keyword accordingly.
LTG0086E	Token-Ring Credit Card Request Configuration failed. Explanation: Card Services would not give IBMTOKCS the configuration that it requested. User Action: Try a different interrupt line by using the INTERRUPT=X statement in your PROTOCOL.INI file. X can be any unused interrupt line in the range 3-15.
LTG0087E	Token-Ring Credit Card RAM MapMemPage failed. Explanation: Card Services would not map the shared-RAM memory on the PC Card to the required memory window. User Action: Try changing the memory window. IBMTOKCS defaults the MMIO memory window to CC00 for the primary PC Card or DC00 for the alternate PC Card. It also defaults the SRAM memory window to D800 for the primary PC Card or D400 for the alternate PC Card. To change the MMIO meory window, add the line MMIO=XXXX to your PROTOCOL.INI file. XXXX can be any unused 8-KB region in the range C000-DE00. To change the SRAM memory window, add the line RAM=XXXX to your PROTOCOL.INI file. XXXX can be any unused 8-KB, 16-KB, 32-KB, or 64-KB region in the range C000-DC00. You might also have to adjust the RAMSIZE keyword accordingly.
LTG0090E	Token-Ring Credit Card Register Client failed. Explanation: Card Services would not register the PC Card callback handler. User Action: Make sure that you have Card Services 2.0 (PCMCIA.SYS) correctly installed.
LTG0091E	Card Services could not be found. Explanation: User Action: Add the appropriate statements to your CONFIG.SYS file so that Card Services will be installed.
LTG0093E	No sockets were found by Card Services. Explanation: The Card Services function GetCardServicesInfo reported that there are no sockets in your computer. This can be for any of the following reasons: Socket Services is not installed or is installed incorrectly. There are no physical sockets on your computer. No PC Card with sockets is installed or is installed incorrectly. User Action: Perform the following steps: Make sure that you have Socket Services installed correctly. Make sure that your computer has physical sockets. Make sure that you have installed the PC Card correctly.
LTG0094I	A Token-Ring Auto 16/4 Credit Card Adapter was not found in any socket in your computer. Explanation: User Action: Insert the PC Card in a socket.
LTG0095E	A NETADDRESS must be specified to boot without the PC Card present in a socket. Explanation: You attempted to boot your computer without a Token-Ring Auto 16/4 Credit Card Adapter inserted in a socket and without a NETADDRESS. User Action: Either insert the PC Card in a socket and reboot your computer or add the NETADDRESS= parameter to PROTOCOL.INI and reboot your computer. By adding the NETADDRESS parameter you can insert the Token-Ring Auto 16/4 Credit Card Adapter after the reboot. Make sure that the address you use is either a locally administered address or the universally administered address on your PC Card. To find out your universally administered address, run the diagnostics program that is on the diskettes that came with your adapter.
LTG0097E	Token-Ring Credit Card MMIO RequestWindow failed. Explanation: Card Services would not give IBMTOKCS access to the MMIO memory window it requested. User Action: Make sure that no other PC Cards are using the memory window requested. IBMTOKCS defaults the MMIO memory window to CC00 for the primary PC Card or DC00 for the alternate PC Card. To change the MMIO memory window, add the line MMIO=XXXX to your PROTOCOL.INI file. XXXX can be any unused 8-KB region in the range C000-DC00.
LTG0098E	Token-Ring Credit Card MMIO MapMemPage failed. Explanation: Card Services would not map the MMIO memory on the PC Card to the requested memory window. User Action: Try changing the MMIO memory window. IBMTOKCS defaults the MMIO memory window to CC00 for the primary PC Card or DC00 for the alternate PC Card. To change the MMIO memory window, add the line MMIO=XXXX to your PROTOCOL.INI file. XXXX can be any unused 8-KB region in the range C000-DC00.
LTG0099E	PROTOCOL.INI did not have a section with a DriverName=IBMTCS$ keyword. Explanation: A common cause of this is not using LAPS to install new drivers. User Action: Use LAPS to install the new PC Card Token-Ring Driver.

DOS NDIS Error Codes

Error Code	Explanation and Action
LTG0022E	A failure during initialization of the IBMTOKCS device driver has occurred. This is a generic initialization failure message. If the IBMTOKCS device driver encounters any errors during initialization, the specific message related to the error will accompany this generic message. Resolve the specific error message that accompanies this message. In addition, ensure that the Protocol Manager device driver, PROTMAN.DOS, exists, and that a DEVICE statement for it exists in the CONFIG.SYS file.

Error Code

Explanation and Action

LTG0022E

A failure during initialization of the IBMTOKCS device driver has occurred. This is a generic initialization failure message. If the IBMTOKCS device driver encounters any errors during initialization, the specific message related to the error will accompany this generic message.

Resolve the specific error message that accompanies this message. In addition, ensure that the Protocol Manager device driver, PROTMAN.DOS, exists, and that a DEVICE statement for it exists in the CONFIG.SYS file.

ODI 16-bit Client Error Codes

Error Code	Explanation and Action
TOKENCS-DOS-32	Driver registered as a NESL Suspend Class producer. Explanation: This is an informational only message. User Action: No action is required.
TOKENCS-DOS-33	Driver registered as a NESL Resume Class producer. Explanation: This is an informational only message. User Action: No action is required.
TOKENCS-DOS-34	Driver registered as a NESL Service Change Class producer. Explanation: This is an informational only message. User Action: No action is required.
TOKENCS-DOS-36	NetWare Event Service Layer (NESL) is Loaded. Explanation: This is an informational only message. User Action: No action is required.
TOKENCS-DOS-50	The board cannot be found or the cable is not attached. Explanation: The PC Card has not been inserted in the PCMCIA socket. User Action: Insert your PC Card in the socket and try again.
TOKENCS-DOS-204	The shared RAM is on incorrect boundary. Explanation: User Action: Change the Shared RAM base address and place it on a 16-KB boundary (C0000, C4000, C8000, CC000, D0000, D4000, D8000, DC000).
TOKENCS-DOS-205	The PC Card did not reset during initialization. Explanation: During initialization, no interrupt occurred. User Action: This can happen if you are using an enabler and it is setting an interrupt level that is different from the interrupt level TOKENCS.COM is using. Check to make sure that both interrupts are the same.
TOKENCS-DOS-206	An interrupt failed to occur during initialization. Explanation: During initialization, no interrupt occurred. User Action: This can happen if you are using an enabler and it is setting an interrupt level that is different from the interrupt level TOKENCS.COM is using. Check to make sure that both interrupts are the same.
TOKENCS-DOS-226	The ROM and shared RAM address ranges overlap. Explanation: The ROM and RAM memory areas are overlapping. User Action: Check the settings in NET.CFG for MEM #1 and MEM #2. MEM #1 determines the ROM (MMIO) base address. MEM #2 determines the Shared RAM base address. If you are using an enabler, check where it is placing the ROM (MMIO) and the RAM address. ROM is 8 KB in size. RAM is usually 16 KB in size.
TOKENCS-DOS-228	The MAX FRAME SIZE in NET.CFG file is too large (Max=17 960) Explanation: The maximum frame size has been exceeded. User Action: Change the maximum frame size to a valid value.
TOKENCS-DOS-229	The MAX FRAME SIZE in NET.CFG file is too small (Min=632). Explanation: The maximum frame size is too small. User Action: Increase the maximum frame size to a valid value.
TOKENCS-DOS-230	The specified MAX FRAME SIZE in NET.CFG is not a multiple of 8. Explanation: The maximum frame size has been set to a value that is not valid. User Action: Change the MAX FRAME SIZE to a multiple of 8.
TOKENCS-DOS-231	The MAX FRAME SIZE in NET.CFG is too big for this PC Card. Explanation: The maximum value at this speed for this PC Card is xx. User Action: Change the MAX FRAME SIZE to a valid value.
TOKENCS-DOS-233	Card Services could not be found. Explanation: TOKENCS.COM could not find Card Services. User Action: Check your CONFIG.SYS and ensure that Card Services is loading. If Card Services support is not wanted, take the PCMCIA keyword out of NET.CFG.
TOKENCS-DOS-235	A Card Services error has occurred. Explanation: You have heard an alternating tone and this message is posted to the panel. This indicates that Card Services was unable to provide the resources requested. User Action: Check your NET.CFG parameters INT, MEM #1, MEM #2. If they are not in NET.CFG, Card Services has a problem. If they are specified in NET.CFG, comment (REM) them out and try again.
TOKENCS-DOS-237	PCMCIA Token-Ring MLID Loaded, but PC Card is not in socket. Explanation: This is an informational only message. User Action: No action is required.
TOKENCS-DOS-246	The DATA RATE specified in NET.CFG must be either 4 or 16 Mbps. Explanation: You have specified an incorrect ring speed. It must be either 4 or 16 Mbps. The DATA RATE keyword is used to set the speed. User Action:
(no message)	Please insert an IBM Turbo 16/4 Token-Ring PC Card 2 or press Esc to avoid loading the driver. Explanation: This message occurs when you have not inserted an IBM Turbo 16/4 Token-Ring PC Card 2 in the computer and have started TOKENCS.COM. User Action: Insert an IBM Turbo 16/4 Token-Ring PC Card 2 at this time or press Esc to leave.

[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]